System and method for early access to captured images

ABSTRACT

Systems and methods are disclosed for early access to captured images including generating and storing within a geospatial database a plurality of placeholder records having information identifying a particular captured image and including at least one geographic image boundary field containing information indicative of a real-world geographic area depicted within the image, an image file location field, and an image status field; receive a plurality of signals from one or more processing computer, at least two of the signals having the information identifying particular captured images, and second information indicative of updates indicating a change in at least one of the image location and image processing status for the image identified by the first information; and populating at least one of the image location and the image processing status of the placeholders within the geospatial database with the information indicative of updates for identified captured images.

INCORPORATION BY REFERENCE

The present patent application claims priority to and is a continuationof the patent application identified by U.S. Ser. No. 13/833,352, filedMar. 15, 2013, all of which the entire contents of which are herebyincorporated herein by reference.

FIELD OF THE DISCLOSURE

The disclosure generally relates to methods and systems for early accessto captured images that typically require lengthy processing times. Moreparticularly the disclosure relates, but is not limited, tomethodologies for early access to captured images through a geospatialdatabase during multiple steps of a post-capture processing stage whichsteps are used to enhance the quality and accuracy of the capturedimages, but prior to the captured images being fully processed andloaded into the geospatial database.

BACKGROUND

In the remote sensing/aerial imaging industry, imagery may be used tocapture views of a geographic area in order to identify and measureobjects and/or structures within the images as well as to be able todetermine geographic locations of points within the image. These aregenerally referred to as “geo-referenced images” and come in two basiccategories:

Vertical Imagery, also known as Nadir Imagery—images captured with acamera pointed vertically downward thus generally capturing the tops ofstructures; and,

Oblique Imagery—images captured with a camera aimed at an anglecapturing the sides, as well as, tops of structures.

One of the uses for vertical imagery and oblique imagery is in theassessment of properties for tax purposes by tax assessors. Inparticular, counties have been requesting aerial image providers to flythe counties to obtain aerial images for assessment purposes for years.For example, Pictometry International Corp., the assignee of the presentpatent application, is an aerial image provider that flies the entirecounty, and then creates a County Image Warehouse, which is a geospatialimage database containing the complete set of oblique images for thatcounty. The county assessor would then use this image warehouse toselect comparable properties and other tasks that are part of their massappraisal effort to establish the property tax base for the town,county, or tax appraisal district.

In many cases, government regulations dictate that the images must becaptured close to the start of the calendar year and that the entireassessment process must be completed by mid-Spring. Traditionally, anairplane or a drone carries one or more cameras to fly geographic areas,such as a county or city to capture vertical imagery and oblique imageryof the geographic areas. Many images can be captured during each flightresulting in very large oblique image libraries of captured images.After the images are captured during the various flight sorties, aninitial process is used to determine the actual geographic boundary ofthe area shown in the images. Thereafter, the images are processedthrough multiple steps in a post-capture processing stage tocolor-balance the images as well as to more accurately geo-reference theimages. Thereafter, the color-balanced and geo-referenced images may bequality-control checked, and then assembled into the County ImageWarehouse.

Once all the flights are complete and all of the portions of the CountyImage Warehouse are assembled, the completed County Image warehouse isthen loaded into a geospatial database of oblique imagery allowing thenewly captured images to be accessed and viewed along with the oldercaptured images as part of an online service, such as Pictometry Online.

Pictometry Online is an online service hosted by a computer system thathas a geospatial database currently containing a massive inventory ofoblique and vertical imagery captured by Pictometry's Capture System.The geospatial database currently contains more than 170,000,000 imagesand is growing significantly each year. Once the captured images areloaded into the geospatial database, the online service allows acustomer to simply navigate to an area using a query and the onlineservice retrieves an oblique image that best represents the area ofinterest and then displays that oblique image in a manner that allowsthe user to both visualize the area of interest and to measure andextract other information contained within the image. The online servicealso allows the user to continuously pan through the massive database ofoblique images, seamlessly moving from one image to the next. Because ofthis capability and because the online method of delivery reduces theinformation technology burden to support the County Image Warehouse,many customers are now switching over to the online delivery mechanism.

The methods discussed above for capturing images, processing images andloading images into the geospatial database have been in practice foryears to permit the geospatial databases to deliver the newly capturedimages to particular customers. Initially, the geospatial databases weredelivered on a hard drive, while more recently the delivery has beenmade online using an online service.

In a standard geospatial database deployment, images are “ingested” intothe database and their geospatial indices are calculated to enable fastsearching based on geospatial coordinates. Typically, the geospatialmetadata and the image pixel data for each captured image are stored inseparate database tables or areas. This is done since typically the typeof access to the metadata and the image pixel data are different andthus for optimization purposes the metadata and image pixel data arestored differently. The separate database tables or areas may be a partof a relational database.

In any event, as the size of the geospatial databases increase, theseingestion steps take increasing amounts of time to complete because theregeneration and optimization of the geospatial indices becomes a moretime consuming task as the number of records continues to grow. As such,common practice is to complete the processing of an “image library” (anarbitrary collection of imagery, typically of a given geospatial area)and then ingest the library into the geospatial database at the sametime since it becomes time and processing prohibitive to ingestindividual groups of images as they come in.

The result of this standard practice is that there is an access delaypresent for new collections of imagery before they are included in amassive image geospatial database. This prevents customers from beingable to access imagery while it is still in the processing stage.Alternatively, the new collections of imagery can be ingested into thegeospatial database, but then any subsequent improvements to the imagequality or image accuracy are not available unless the new collectionsof imagery have been re-ingested into the geospatial database. Thisheavy burden, both administratively and from a resource consumptionstandpoint, might be possible for special projects, such aspost-disaster flights, but it is not repeatable on a routine basis whenoperating a large fleet of aircraft that are generating thousands of newprojects each capture season.

The conventional method discussed above results in a one to three monthdelay between when the images are captured, to when the images areavailable to be accessed by the customer. During this time period, thecaptured images are going through multiple discrete steps of theprocessing stage in which the image quality and/or the image accuracy isbeing enhanced. Exemplary steps of the processing stage includecolor-balancing, geo-referencing, quality control checks, and assemblingthe captured images into image warehouses. Since the images are requiredto be captured close to the start of the calendar year and the entireassessment process must be completed by mid-Spring, the assessors mustappraise the properties within the entire territory in a very shortamount of time. In many cases, this dictates that the county must hireor maintain a larger staff than would otherwise be needed in order toprocess this large number of properties in a short amount of time.

As prudent managers of taxpayer funds, the counties are interested inways to reduce the impact of the conventional methodology by increasingthe amount of time that their assessors have to appraise the propertiesin their territory. The present disclosure is directed to a new andimproved computerized methodology that is designed to provide access tothe captured images in a much shorter period of time than theconventional process.

SUMMARY

Methods and systems for addressing the problems discussed above aredisclosed. The problem of enhanced staffing by the counties is addressedby early access methodologies that provide access to the captured imagesthrough the geospatial database during multiple steps of thepost-capture processing stage used to enhance the quality and accuracyof the captured images, but prior to the captured images being fullyprocessed and loaded into the geospatial database. Thus, counties areable to access the captured images through the geospatial databasebetween one to three months earlier than the prior methodology resultingin more time for the assessors to be able to appraise the parcels.

Early access to the captured images can be implemented by storing thecaptured images and metadata for the captured images into one or moreprocessing directories on one or more processing drives, and thengenerating and storing placeholder records within the geospatialdatabase prior to completing the processing stage for enhancing thequality and/or accuracy of the captured images. The metadata may includegeo-referencing information indicative of a position, orientation andcharacteristics of the camera used to capture the image that can be usedto derive real-world geographic coordinates of the area and structuresdepicted within the image. Techniques for obtaining and using theposition, orientation and characteristics of the camera to derivereal-world coordinates of the area and structure depicted within theimage are discussed in U.S. Pat. No. 7,424,133 which is herebyincorporated herein by reference.

The placeholder records can be generated and stored prior to thebeginning of the post-capture processing stage. Each of the placeholderrecords are for a particular captured image and include a geographicimage boundary field populated with information indicative of thegeographic footprint of the captured image so that the captured imagecan be located during a request for captured images of a particulargeographic location or region sent to the one or more servers by aclient application running on an operator user device.

The placeholder records also include an image file location field, andan image status field for the particular captured image. The image filelocation field for each captured image may identify logic for retrievingthe captured image and/or its metadata which may include thegeo-referencing information associated with the captured image by theone or more servers from a project directory that is separate from thegeospatial database, but accessible by the one or more server. Theproject directory is also accessible by one or more processing computerthat is being used to implement a step of the post-capture processingstage. The image status field may store information indicative of thecaptured image being in the post-capture processing stage, or the stateor status of the captured image within the post-capture processingstage. For example, the image status field may store informationindicating that geo-referencing has been completed, but quality controlhas not been completed.

Because the placeholder record for the captured image has the generalgeospatial bounds of the image footprint for the image, the placeholderrecord can be located during a search for a particular geographiclocation or region from the customer's computer. The one or more servermay execute computer executable code that causes the one or more serverto access and read the image status field of the placeholder recordwithin the image geospatial database to determine whether the capturedimage is fully processed, and if not, the one or more server uses theimage file location field to locate the image and/or metadata on theprocessing drive(s) and retrieves the image and/or full metadata fromthe processing drive(s) rather than from the geospatial database.

As the captured images are processed during steps of the post-captureprocessing stage, updates to the captured images and/or the metadata arestored in the processing directories of the processing drive(s), ratherthan in the geospatial database. When the post-capture processing stageof a library of captured images has been completed including all qualitycontrol checks, the captured images and associated metadata from thelibrary can then be fully ingested into the geospatial database. Becausethe images in the library that have completed the post-captureprocessing stage have the metadata indices of their placeholder records,the captured images and their associated metadata are loaded into theplaceholder records to convert the placeholder records into permanentrecords. Further, the image status field is updated to reflect that thepost-capture processing stage is complete. Thereafter, the geospatialindices update can be run on the geospatial database once ingestion iscomplete and all of the placeholder records for images in the libraryhave been converted into permanent records.

Thereafter, the images (including the finished metadata and pixelcontent) will be retrieved directly from the repositories within thegeospatial database. In other words, if the image status field indicatesthat the captured image has been fully processed and the placeholderrecord has been converted into a permanent record for the image, thenthe metadata will be accessed and retrieved from the permanent recordfor the captured image as would normally be the case.

The early access methodology described within the present disclosure maynot be as efficient as the conventional methodology which retrieves themetadata from the geospatial database; however customers are willing toendure this slight additional time delay in order to be able to getearly access to the imagery. Similarly, when a client requests to viewthe image the server software interprets the status field and uses the“image file location field” in order to locate the image pixel data andsends that data to the client application on the operator user devicerather than retrieving the image pixel data from the geospatial databaseimage repository.

Because the one or more server accesses the captured image and itsmetadata from the processing drive(s) during the post-capture processingstage, improvements in the captured image and/or its metadata due tocompleted processing steps are reflected in the image and/or metadatadelivered to the client application even though the captured imageand/or its metadata has not been ingested into the geospatial database.

As the image location or status of the captured images is changed duringthe steps of the post capture processing stage, updates are generated byone or more processing computer and transmitted to the one or moreservers of a computer system hosting the geospatial database.Information indicative of the updates is received by the one or moreservers and is used to populate at least one of the image file locationfield and the image status field of the placeholder records within thegeospatial database.

In one embodiment, the image location for each captured image mayidentify logic for retrieving the captured image and/or its metadataincluding geo-referencing information associated with the captured imageby the one or more servers from a project directory that is separatefrom the geospatial database. The project directory may also beaccessible by the one or more processing computer that is being used toimplement a step of the processing methodology.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate one or more implementationsdescribed herein and, together with the description, explain theseimplementations. In the drawings:

FIG. 1 is a block diagram of an exemplary computer system constructed inaccordance with the present disclosure.

FIG. 2 is a block diagram of an exemplary storage system for storing ageospatial database having post-capture processed images, and imagesthat are in a post capture processing stage on multiple processingdrives in accordance with the present disclosure.

FIG. 3 is a flow diagram of a computerized process in which placeholderrecords are added to a geospatial database and updated as capturedimages are processed during multiple steps of a post capturingprocessing stage.

FIG. 4 is a flow diagram of a computerized process of an online servicehaving servers hosting a geospatial database for presenting an image ofa geographic area upon request for at least one image of the geographicarea.

FIG. 5 is a flow diagram of a part of the computerized process of FIG. 4in which a status indicator for the at least one image is presentedalong with a visual depiction of the image.

FIG. 6 is an exemplary screen shot of an image and a geospatialdepiction of status of the image in accordance with the presentdisclosure on a display of an operator user device.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

The mechanisms proposed in this disclosure circumvent the problemsdescribed above. The present disclosure describes a method and systemfor performing sensitive geo-spatial processing in non-sensitiveoperator environments.

In one embodiment, a computer system comprises one or morenon-transitory computer readable mediums storing computer executablecode that when executed by one or more servers of the computer systemcause the one or more servers to generate and store a plurality ofplaceholder records for captured images within a geospatial database.The placeholder records may have information identifying a particularcaptured image, at least one geographic image boundary field containinginformation indicative of a real-world geographic area depicted withinthe image, an image file location field, and an image status field. Theserver may receive a plurality of signals from one or more processingcomputer, at least two of the signals having the information identifyingparticular captured images and indicative of updates indicating a changein at least one of the image location and image processing status forthe image. The server may populate at least one of the image filelocation field and the image status field of the placeholder recordswithin the geospatial database with the information indicative ofupdates for identified captured images.

Additionally, the placeholder records may have or be linked to at leastone metadata field adapted to store geo-location information for acaptured image, and at least one image raster data field adapted tostore at least a portion of the captured image, and the one or moreservers may populate the at least one metadata field and the at leastone image raster data field after processing steps have been completedfor the captured images, for example, after at least two processingsteps.

In one embodiment, the one or more server may receive a request for atleast one image of a geographic area from a client application of anoperator user device; query records within a geospatial database tolocate one or more records of images accessible by the geospatialdatabase and depicting at least a portion of the geographic area; for atleast one record located in the query, read a first field within therecord indicating a status of the image; and read a second field withinthe record responsive to the status of the image indicating that theimage is not stored in the geospatial database, the second field havinginformation indicative of a location of the image in a non-transientmemory; and present the image to the client application of the operatoruser device utilizing the information of the second field to identifythe location of the image in the non-transient memory.

In one embodiment, the server may present at least a portion of theimage to the client application of the operator user device with astatus indicator indicating a post-capture processing status of theimage.

DESCRIPTION

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by anyone of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the inventive concept. Thisdescription should be read to include one or more and the singular alsoincludes the plural unless it is obvious that it is meant otherwise.

Further, use of the term “plurality” is meant to convey “more than one”unless expressly stated to the contrary.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Software includes one or more computer executable instructions that whenexecuted by one or more component cause the component to perform aspecified function. It should be understood that the algorithmsdescribed herein are stored on one or more non-transient memory.Exemplary non-transient memory includes random access memory, read onlymemory, flash memory or the like. Such non-transient memory can beelectrically based or optically based.

Referring now to the drawings, and in particular to FIG. 1, showntherein and designated by a reference numeral 100 is an exemplarycomputer system constructed in accordance with the present disclosure.The computer system 100 can be a system or systems that are able toembody and/or execute the logic of the processes described herein. Thelogic embodied in the form of software instructions or firmware may beexecuted on any appropriate hardware which may be a dedicated system orsystems, or a personal computer system, or distributed processingcomputer system. In particular, the logic can be implemented in astand-alone environment operating on a single computer system, or thelogic can be implemented in a networked environment such as adistributed system using multiple computers and/or processors.

For example, the computer system 100 may be distributed, and may includea controlled datacenter 110 acting as a host system, communicating withone or more Customer Entity 112 and/or Customer Operator 114 utilizingone or more operator user device(s) 116 via a network 118. The network118 can be the Internet or other network. The controlled datacenter 110may include one or more servers 120 (which will be referred tohereinafter as the server 120) configured to communicate with thenetwork 118 via one or more gateways 122. If the network 118 is theInternet, then the client application forming the primary user interfaceof the computer system 100 for operator user devices 116 may be abrowser receiving content through a series of web pages. The clientapplication forming the primary user interface may be another type ofinterface, such as a Windows-based application. This method may also beused when deploying the computer system 100 in a stand-aloneenvironment.

The network 118 can be almost any type of network such as Internet andInternet 2 networks. If the network 118 exists in an Internetenvironment, network 118 may be TCP/IP-based. It is conceivable that inthe near future, more advanced networking topologies may be used.

The server 120 can be networked with a LAN 124. The gateway 122 is anentity responsible for providing access between the LAN 124 and thenetwork 118. The gateway 122 can also be used as a security means toprotect the LAN 124 from attack through external networks such as thenetwork 118. The LAN 124 and the one or more servers 120 may be securedfrom unauthorized access physically and/or logically.

The LAN 124 network can be based on a TCP/IP network such as theInternet, or it can be based on another underlying network transporttechnology. The preferred embodiment uses an Ethernet network withTCP/IP because of the availability and acceptance of underlyingtechnologies, but other embodiments may use other types of networks suchas Fibre Channel, SCSI, Gigabit Ethernet, etc.

As discussed above, in one embodiment, the controlled datacenter 110includes the one or more servers 120 (which will be referred tohereinafter as the server 120). The configuration of the server hardwarewill depend greatly upon the requirements and needs of the particularembodiment of the computer system 100. The servers 120 include one ormore server processors 126 (which will be referred to hereinafter as theserver processor 126). Typical embodiments will include multiple servers120 with load balancing to increase stability and availability. It isenvisioned that the servers 120 will include database servers 120 a andapplication/web servers 120 b. The database servers 120 a may beseparated from the application/web servers 120 b to improve availabilityand also to provide the database servers 120 a with improved hardwareand storage and/or security. Of course, the controlled datacenter 110may contain one or more other processors. Functions described herein ascarried out by the server processor(s) 126 or operator user device(s)116 may be carried out by one or more other processors in the controlleddatacenter 110 or the computer system 100.

The operator user device 116 utilized by the Customer Entity/Operator112/114 can be any number and type of devices. The operator user device116 typically includes one or more user device processor 128 (which willbe referred to hereinafter as the user device processor 128) running aclient application, which may be a browser. The most typical scenario ofthe operator user device 116 involves the customer operator 114, using acomputer 130 with a display 132, keyboard 134, and mouse 136. Theoperator user device 116 may include the user device processor 128. Thedisplay 132 can be a single monitor or multiple adjacent monitors.Typically, the operator user device 116 uses a type of software called a“browser” as indicated by a reference numeral 138 to render HTML/XHTMLcontent that is generated when requesting resources from a source, suchas the controlled datacenter 110. In one embodiment, the computer system100 is designed to be compatible with major Web Browser vendors (e.g.,Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, and Opera).Other embodiments may wish to focus on one particular browser dependingupon the common user base using the computer system 100.

The operator user device 116 can also be implemented as a portabledevice such as a laptop computer 140 (or handheld computer) or apen-based or tablet computer. In one embodiment, the operator userdevice 116 can be a “dumb” device with the display 132 and keyboard 134with at least a portion of computer processing taking place elsewhere.Current embodiments of computer system 100 can also be modified to useany of these or future developed devices.

One or more customer 112 may communicate with the controlled datacenter110 directly and/or via the network 118. The one or more customer 112may request and receive early access to images of geographic regions ofinterest.

The computer system 100 may also include one or more processingcomputer(s) 150-1 . . . 150-n. The processing computer(s) 150-1 . . .150 n may be internal and/or external to the controlled datacenter 110and may contain one or more processors that are networked with theservers 120.

The computer system 100 is designed in this way as to provideflexibility in its deployment. Depending upon the requirements of theparticular embodiment, the system logic could be designed to work inalmost any environment such as a desktop application, a web application,or even simply as a series of web services.

The hardware and software of the computer system 100 may be designed forflexibility, scalability, and security. Although some specifics forsoftware and hardware components may be mentioned herein, it will beunderstood that a wide array of different components could besubstituted, such as using different database vendors or even replacingthe databases with XML-based document stores.

When the computer system 100 is used to execute the logic of theprocesses described herein, such computer(s) and/or execution can beconducted at a same geographic location or multiple different geographiclocations. Furthermore, the execution of the logic can be conductedcontinuously or at multiple discrete times.

In general, the computer system 100 is capable of displaying andprocessing geo-referenced imagery, such as aerial imagery, to measurewithin the imagery and/or identify objects within the imagery. Thecomputer system 100 will be described by way of example utilizing aerialimages shown on the display 132 of the computer 130. However, it shouldbe understood that the computer system 100 can use other types ofimages, such as architectural images.

FIG. 2 is a block diagram of an exemplary storage system 200 for storinga geospatial database 210 having post-capture processed images, andimages that are in a post-capture processing stage on multipleprocessing drives in accordance with the present disclosure. The one ormore server 120 a may store and access one or more geospatial database210 in non-transitory memory. The geospatial database 210 may storerecords 212 indicative of captured images and metadata for the capturedimages. The records 212 may be permanent records 214 or placeholderrecords 216. In permanent records 214, associated processed capturedimages 218 and associated metadata have completed post-captureprocessing and may be used by the customer as a finished product forfull analyses. The processed captured images 218 and associated metadatafor the permanent record 214 are stored in the geospatial database 210.

Placeholder records 216 can be generated and stored prior to thebeginning of the post-capture processing stage for the captured images.Each of the placeholder records 216 are for a particular in-processcaptured image 220. The placeholder record 216 includes a geographicimage boundary field populated with geo-location information indicativeof the geographic footprint of the in-process captured image 220. Thegeographic image boundary field allows the in-process captured image 220to be located during a request for in-process captured images 220 of aparticular geographic location or region sent to the one or more servers120 by a client application running on an operator user device 116.

The records 212 also include an image file location field and an imagestatus field for the particular in-process or processed captured image218, 220. The image file location field for each in-process capturedimage 220 may identify logic for retrieving the in-process capturedimage or its metadata. The image file location field may include thelocation information associated with the in-process captured image 220by the one or more server processors 126 to locate the storage locationof the in-process captured image 220 and associated metadata. Forexample, the image file location field may include informationindicative of a filename and project directory where the in-processcaptured image 220 and associated metadata are stored. The projectdirectory may be a logical name associated with a particular physicaldrive or drives. The image status field may store information indicativeof the processed captured image 218 being in the post-capture processingstage, or the state or status of the in-process captured image 220within the post-capture processing stage. For example, the image statusfield may store information indicating that geo-referencing has beencompleted, but quality control has not been completed.

Of course, it should be understood that a plurality of fields may beassociated with the records 212. Further, the information in thegeographic image boundary field, the image file location field, and theimage status field, may be stored in more than one field. In oneexample, the following fields and exemplary data are associated with anexemplary record 212:

-   -   Name: OKOKLA022013NeighObliq30E_060116    -   Capture Date: Jan. 16, 2006 13:14    -   GPS Time Code: 152055.953504    -   Shot Level: Neighborhood    -   Direction: East    -   Per Pixel Resolution: 0.51 (feet/pixel)    -   Image Size: 4008×2672    -   Upper Left Shot Corner Lat: 35.4723    -   Upper Left Shot Corner Lon: −97.5142    -   Upper Right Shot Corner Lat: 35.4719    -   Upper Right Shot Corner Lon: −97.4783    -   Lower Right Shot Corner Lat: 35.4785    -   Lower Right Shot Corner Lon: −97.5233    -   Lower Left Shot Corner Lat: 35.4782    -   Lower Left Shot Corner Lon: −97.5244    -   Camera Location Lat: 35.4746    -   Camera Location Lon: −97.5349    -   Camera Altitude: 4322.49    -   Average Elevation: 1202.32    -   Camera Pitch: −0.54346    -   Camera Roll: 53.40959    -   Camera Azimuth: 177.42867    -   Focal Length: 84.932    -   Focal Plane Width: 36.072    -   Focal Plane Height: 24.048    -   Principal Point Offset X: 51.444    -   Principal Point Offset Y: 41.656    -   Radial Distortion Coefficient 1: −6.1122276e-010    -   Radial Distortion Coefficient 1: 8.6850581e-017    -   Radial Distortion Coefficient 1: 8.8033733e-033    -   Tessellated Ground plane rows: 14    -   Tessellated Ground plane columns: 21    -   Tessellated Ground plane edge ratio: 1.200000    -   Named Library: OKOKLA06    -   Camera Serial Number: 8479    -   Early Access Status: Stage 4    -   Early Access Path:        \\Xorn5\Processing2\OKOKLA06\Sortie7\FlightPlan43\        OKOKLA022013NeighObliq30E_060116.psi

In the preceding example, the geographic image boundary field isrepresented by multiple fields storing latitude and longitude data forthe image (for example, “Upper Left Shot Corner Lat” and “Upper LeftShot Corner Lon”). The image file location field is represented by an“Early Access Path” field storing a computer file path locationincluding a computer drive name, computer directory names, and filename. The image status field is represented by an “Early Access Status”field storing information indicative of which stage of processing theimage has completed. It should be understood that these fields aremerely exemplary and the information may be stored in more or fewerfields and may be named and/or formatted differently.

The in-process captured image 220 and associated metadata may be locatedin a project directory on a processing drive 230 that is separate fromthe geospatial database 210, but accessible by the one or more serverprocessor 126. The processing drive 230 may be stored on the same server120 or a different server 120 than the geospatial database 210. Theproject directory on the processing drive 230 is also accessible by oneor more processing computer 150 that is being used to implement one ormore steps of the post-capture processing stage.

The one or more processing computer 150 runs post-capture processingsoftware to implement one or more steps of the post-capture processingstage. The post-capture processing software is configured to avoidmoving or locking the imagery such that the imagery cannot be accessed.As such, when work is being done on a particular image, such work isdone on a working copy and as soon as the work is complete, the workingcopy may overwrite the previous copy, thus making the working copyimmediately available to the end user. When the placeholder record 216for the image is added into the geospatial database 210 for earlyaccess, the resulting metadata record index may be stored with the imageon the processing drive 230 such that any changes in status can berecorded in the geospatial database 210 allowing the server 120 to actaccordingly. Since the metadata may not be modified in the geospatialdatabase 210, there is no need for the time consuming and resourceexpensive regeneration of geospatial indices. A particular image'sgeospatial bounds contained in the geospatial database 210 may beslightly off so a selection along the edge of the image may not retrievethat particular record, but if adequate overlap is maintained whencollecting the imagery, an adjacent image will be retrieved instead,still providing the client or operator with complete coverage of thearea. The important feature is that when the image is retrieved by thegeospatial database 210, the further processed and more accuratemetadata is what is sent with the image pixel content to the operatoruser device 116 such that any measurements taken upon the image enjoythe greater accuracy that occurs as images progress through thepost-capture processing chain.

In one embodiment, the in-process captured images 220 and associatedmetadata may be stored on a removable portable drive. For example, inthe case of post-disaster response, images may be needed immediately andso may be accessed by the server processor 126 from the removableportable drive directly after a plane capturing the images lands, oreven before the plane lands. In this case, the server 120 would form theplaceholder records 216 in the geospatial database 210 for the imagefiles, while the image files remain on the removable portable drive.

Because the placeholder record 216 for the in-process captured image 220has the general geospatial bounds of the image footprint for thein-process captured image 220 (for example, in the geographic imageboundary field), the placeholder record 216 can be located during asearch for a particular geographic location or region from thecustomer's computer. The one or more server processor 126 may executecomputer executable code that causes the one or more server processor126 to access and read the image status field of the placeholder record216 within the image geospatial database 210 to determine whether thecaptured image is a fully processed captured image 218 or an in-processcaptured image 220. If the image is an in-process captured image 220,then the one or more server 120 may use the image file location field tolocate the in-process captured image 220 and/or the associated metadataon the processing drive(s) 230 and to retrieve the in-process capturedimage 220 and/or full associated metadata from the processing drive(s)230 rather than from the geospatial database 210.

As the in-process captured images 220 are processed during steps of thepost-capture processing stage, updates to the in-process captured images220 and/or the associated metadata are stored in the processingdirectories of the processing drive(s) 230, rather than in thegeospatial database 210. When the post-capture processing stage of alibrary of in-process captured images 220 has been completed includingall quality control checks, the in-process captured images 220 andassociated metadata from the library can then be fully ingested into thegeospatial database 210 as processed captured images 218. Because thein-process captured images 220 in the library that have completed thepost-capture processing stage have the metadata indices of theirplaceholder records 216, the in-process captured images 220 andassociated metadata are loaded into the placeholder records 216 toconvert the placeholder records 216 into permanent records 214. Further,the image status field may be updated to reflect that the post-captureprocessing stage is complete. Thereafter, the geospatial indices updatecan be run on the geospatial database 210 once ingestion is complete andthe placeholder records 216 for processed captured images in the libraryhave been converted into permanent records 214.

Thereafter, the processed captured images 218 (including the finishedassociated metadata and pixel content) will be retrieved directly fromthe repositories within the geospatial database 210. In other words, ifthe image status field indicates that the captured image 218 has beenfully processed and the placeholder record 216 has been converted into apermanent record 214 for the image 218, then the metadata will beaccessed and retrieved from the permanent record 214 for the processedcaptured image 218 as would normally be the case. That is, the earlyaccess is replaced by normal access of the processed captured images 218in the system.

FIG. 3 is a flow diagram of a computerized process 300 in whichplaceholder records 216 are added to a geospatial database 210 andupdated as in-process captured images 220 are processed during multiplesteps of a post capture processing stage. The process 300 may begin withthe capture of images, such as aerial images, in step 302. The serverprocessor 126 may add placeholder records 216 into the geospatialdatabase 210 for the in-process captured images 220 in step 304, whilethe in-process captured images are stored elsewhere, such as inprocessing drive(s) 230. The server processor 126, in step 306, may usethe placeholder records 216 to make the in-process captured images 220available to a user of the system. In step 308, the in-process capturedimages 220 are processed and then, after one or more processing steps,the placeholder record 216 may be updated, as shown in step 310. In oneexample, the placeholder record 216 may be updated after at least twoprocessing steps. The placeholder record 216 may be updated with thestatus of the processing and/or the latest metadata for the in-processcaptured image 220.

Referring now to decision step 312, if the processing is incomplete, theprocess 300 may return to steps 308 and 310 to continue the processingof the in-process captured images 220 and continue updating theplaceholder record 216. If the processing is complete, then the process300 proceeds to step 314 in which the server processor 126 may load thenow processed captured images 218 and the associated metadata into thegeospatial database 210 and update the placeholder record 216 into apermanent record 214.

FIGS. 4 and 5 depict a process flow diagram of steps of an exemplarymethod 400 for receiving and processing requests for data processing ofa geographic region of interest in accordance with the presentdisclosure. FIG. 4 is a flow diagram of a computerized process 400 of anonline service having servers 120 hosting the geospatial database 210for presenting an image of a geographic area upon request for at leastone image of the geographic area. The server 120 may receive one or morerequest, for example, from customer entity 112, for one or more imagesof a geographic area, as illustrated in step 402. The request mayindicate the geographic area by address, latitude and longitude,community, zip code, or other geographic or subject indicator. In step404, the server processor 126 may query the geospatial database 210 forone or more record 212 that indicate, such as with information in thegeographic image boundary field, that the corresponding image for therecord depicts the geographic area of interest requested.

As illustrated in decision step 406, if one or more appropriate record212 is not located by the server processor 126, then the process 400ends in step 408. If one or more appropriate record 212 is located, thenthe process 400 moves to decision step 410. In decision step 410, therecord 212 is queried to determine if the image corresponding to therecord 212 is a processed captured image 218 stored within thegeospatial database 210. If so, the process 400 moves to step 412 inwhich the server processor 126 presents the processed captured image 218from the geospatial database 210 to the customer entity 112. If theimage corresponding to the record 212 is not a processed captured image218 stored within the geospatial database 210, but is rather anin-process captured image 220, then the server processor 126, in step414, utilizes the image file location field in the placeholder record216 to determine the storage location of the in-process captured image220. Then, in step 416, the server processor 126 may present thein-process captured image 220 to the customer entity 112 from thedetermined location.

FIG. 5 is a flow diagram of a part 400 b of the computerized process 400of FIG. 4 in which a status indicator for the at least one image ispresented along with a visual depiction of the image. As described inconjunction with FIG. 4, the server processor 126 may receive a requestfor one or more images of a geographic area (step 402) and query thegeospatial database 210 for one or more images fulfilling the request(step 404). In the example of FIG. 5, the server processor 126 may alsoutilize the record 212 to determine the status of the image, as shown instep 420. For example, the server processor 126 may utilize informationin the image status field, as previously described. The server processor126 may present the image to the customer entity 112 along with a statusindicator, as shown in step 422. For example, the indicator may showthat the image is not fully processed, or may indicate the current stagein the processing steps of the image. In one example, the indicator maybe a “badge” overlaid with the image, for example, across one or morecorners of the image.

FIG. 6 is an exemplary screen shot 600 of an exemplary system inaccordance with the present disclosure on a display 132 on a user device116. In one embodiment, the display 132 may display a navigable map 602containing information indicative of which geographic areas havein-process captured images 220 available for early access viewing. Inthis example, the shaded area 604 of the map 602 indicates theavailability of the in-process captured images 220. In one example,multiple in-process captured image(s) 220 may be available for displayand the map 602 may indicate multiple image availability through changesin shading of the shaded area 604. For example, darker shading mayindicate that more in-process captured images 220 are available than inlighter shaded areas. In one example, the shading is one or more color.In one embodiment, the map 602 may contain information as to the statusof the in-process captured images 220.

The system may allow a user to select one or more geographic areas ofinterest in the map 602, for example, by selection of points, parcels,objects, buildings, geographic areas, input of an address, latitudelongitude, coordinates, etc. The selection may send a signal to theserver processor 126 indicative of the geographic area of interest. Theserver processor 126 may then query the geospatial database 210 for oneor more records 212 containing corresponding geographic information,such as may be contained in the geographic image boundary field. Aspreviously described, the server processor may then locate and displaythe in-process captured image(s) 220 for the geographic area of interestselected. In this example, the in-process captured image 220 isdisplayed adjacent to the map 602. The in-process captured images 220may be displayed with the status indicator, such as badge 606, overlaidwith the image. For example, in FIG. 6, the badge 606 is across theupper right corner of the image. Of course, it should be understood thatthe status indicator may be displayed in other ways, for example, as atext field 608. It should also be understood that the in-processcaptured images 220 may be made available in other ways, such asindividual screens or reports.

CONCLUSION

Currently, access to complex data-rich images may require significantwait times while the images are being processed. The problem may beaddressed, for example, with system and methods for providing earlyaccess to the images during the processing stage, while avoiding costlyiterative data ingestion to the geospatial database, through the use ofplaceholder records in the geospatial database and secondary storagelocations for the in-process images.

The foregoing description provides illustration and description, but isnot intended to be exhaustive or to limit the inventive concepts to theprecise form disclosed. Modifications and variations are possible inlight of the above teachings or may be acquired from practice of themethodologies set forth in the present disclosure.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure. In fact, many of these features may becombined in ways not specifically recited in the claims and/or disclosedin the specification. Although each dependent claim listed below maydirectly depend on only one other claim, the disclosure includes eachdependent claim in combination with every other claim in the claim set.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such outside of the preferred embodiment. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

It should be understood that not all of the steps described arenecessary or necessarily in the order described and that one or more ofthe steps may be executed on different portions of the computer system100.

1-10. (canceled)
 11. A computer system comprising one or morenon-transitory computer readable mediums storing computer executablecode that when executed by one or more servers of the computer systemcause the one or more servers to: receive a request for at least oneimage of a geographic area from a client application of an operator userdevice; query records within a geospatial database to locate one or morerecords of images accessible by the geospatial database and depicting atleast a portion of the geographic area; and present at least a portionof the image to the client application of the operator user device witha status indicator indicating that the image is not fully processed. 12.The computer system of claim 11, wherein the computer executable code isconfigured to cause the one or more servers to present the statusindicator geospatially.
 13. The computer system of claim 12, wherein thegeospatial presentation of the status indicator is depicted as aboundary overlaid on a geospatial map or display.
 14. The computersystem of claim 11, wherein the status indicator of the image includes astatus of at least one of color-balancing the image, quality controlprocessing of the image, geo-referencing the image, whether processingof the image has begun.
 15. The computer system of claim 11, wherein theimage is a first image, and wherein the computer executable code thatwhen executed by one or more servers of the computer system cause theone or more servers to present at least a portion of a second image tothe client application of the operator user device with a statusindicator indicating that the image is fully processed.